Cleanup batches inside the engine if they were not released explicity before disconnection #8341
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…y before disconnection. This avoids a resource leak (it's mostly about TempSpace).
AlexPeshkoff
approved these changes
Dec 5, 2024
|
It it worth backporting into v4/v5? |
dyemanov
added a commit
that referenced
this pull request
Dec 10, 2024
…y before disconnection. This avoids a resource leak (it's mostly about TempSpace). (#8341)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This avoids a resource leak (it's mostly about
TempSpace). Easy to reproduce - just open a batch, push a significant number of records through the batch and disconnect. You'll get an assertionfb_assert(m_tempCacheUsage == 0);inside~GlobalObjectHolder()and may also notice temporary files still existing.Init/cleanup logic of
JBatchis changed to matchJResultSetandJReplicator.